Everything about Capability-based Addressing totally explained
In
computer science,
capability-based addressing is a scheme used by some computers to control access to memory. Under a capability-based addressing scheme,
pointers are replaced by protected objects (called
capabilities) that can only be created through the use of
privileged instructions which may only be executed by the
kernel (or some other privileged process authorised to do so). This effectively allows the kernel to control which processes may access which objects in memory without the need to use separate
address spaces and therefore requiring a
context switch when an access occurs. This allows an efficient implementation of
capability-based security.
Practical implementations
Two techniques are available for implementation:
- Require capabilities to be stored in a particular area of memory that can't be written to by the process that will use them. For example, the Plessey System 250 required that all capabilities be stored in capability-list segments.
- Extend memory with an additional bit, writable only in supervisor mode, that indicates that a particular location is a capability. This is a generalization of the use of tag bits to protect segment descriptors in the Burroughs large systems, and it was used to protect capabilities in the IBM System/38.
While popular in research systems, capability-based addressing isn't commonly available in commercial computer systems, with a few exceptions (for example
Plessey System 250). The most widely sold architecture using capability-based addressing is the
IBM System/38 (but users of these systems were rarely aware of its sophisticated memory-addressing model) .
The designers of the System/38's descendent systems,
AS/400 and
iSeries, removed capability-based addressing. The reason given in for this decision is that they could find no way to revoke capabilities (although patterns for implementing revocation in capability systems had been published as early as 1974, even before the introduction of System/38).
Chronology of systems adopting capability-based addressing
1969: System 250 - Plessey Corporation
1978: System/38 - IBM
Further potential additions can be found here: (External Link
).
Further Information
Get more info on 'Capability-based Addressing'.
|
External Link Exchanges
Do you know how hard it is to get a link from a large encyclopaedia? Well we're different and will prove it. To get a link from us just add the following HTML to your site on a relevant page:
<a href="http://capability-based_addressing.totallyexplained.com">Capability-based addressing Totally Explained</a>
Then simply click through this link from your web page. Our crawlers will verify your link, extract the title of your web page and instantly add a link back to it. If you like you can remove the words Totally Explained and embed the link in article text.
As long as your link remains in place, we'll keep our link to you right here. Please play fair - our crawlers are watching. Your site must be closely related to this one's topic. Any kind of spamming, dubious practises or removing the link will result in your link from us being dropped and, potentially, your whole site being banned. |
